Micron Document




Object-oriented programming
part 35/57 · 94.0 KB total
──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
Paul Graham, a well-known computer scientist, believes big companies like OOP because it helps manage large teams of average programmers. He argues that OOP adds structure, making it harder for one person to make serious mistakes, but at the same time restrains smart programmers.cite-ref-graham-72-0[72] Eric S. Raymond, a Unix programmer and open-source software advocate, argues that OOP is not the best way to write programs.cite-ref-eric-s-raymond-2003-42-2[42]

Richard Feldman says that, while OOP features helped some languages stay organized, their popularity comes from other reasons.cite-ref-73[73] Lawrence Krubner argues that OOP doesn't offer special advantages compared to other styles, like functional programming, and can complicate coding.cite-ref-lawrence-74-0[74] Luca Cardelli says that OOP is slower and takes longer to compile than procedural programming.cite-ref-badprop-40-2[40]

──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────